What does this PR do?

Fixes inconsistent disabled state for booking actions. Several actions (Edit location , Add Guests, Reroute, Reassign) were hardcoded to disabled: false, allowing users to see enabled buttons on cancelled, rejected, or past bookings.

Users could see enabled "Edit Location" or "Add Guests" buttons on bookings that were already cancelled/rejected/past, which doesn't make sense functionally.

• Fixes #XXXX (GitHub issue number)
• Fixes CAL-XXXX (Linear issue number - should be visible at the bottom of the GitHub issue description)

Changes -

• change_location, add_members, reroute, reassign now use isActionDisabled() instead of hardcoded disabled: false
• cancel action now properly checks for isCancelled and isRejected states
• reschedule and reschedule_request now checks for isCancelled and isRejected states

Visual Demo (For contributors especially)

Video Demo (if applicable):

• before:

• after:

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

Tested locally and verified with before/after screen recordings.